Catalog of HyTime Architectural Forms and HyTime SGML Specification Version 2.0,
June 28, 1993
By Charles F. Goldfarb

This document contains an unofficial compilation of the formal SGML specifications from the HyTime Standard (ISO/IEC 10744:1992), cross-referenced to the text that describes them, and with known errors corrected. The current version expands on the original by including the formal specifications of useful element types, notations, and instances from Annex A. of the standard. The material in this document is excerpted from the pre-publication review edition of "The HyTime Handbook", which I hope will be available for limited distribution in the fall of 1993.

COPYRIGHT AND LICENSES

This document is distributed in both printed and machine-readable form. It contains formal SGML specifications derived from ISO/IEC 10744, and additional text and cross-references from The HyTime Handbook. The document as a whole is subject to the following copyright notice and license:

(C) Charles F. Goldfarb 1993.
Permission to copy in any form is granted for use with conforming 
HyTime systems and applications as defined in ISO/IEC 10744, provided 
that all copies are accurate and complete in every respect, including 
this notice.

The above license is intended to encourage the dissemination of the formal SGML specifications, while assuring that essential information about variations from the text of the standard (see below) is disseminated with them.

The formal SGML specifications are individually subject to the following copyright notice and license:

(C) International Organization for Standardization 1992.
Permission to copy in any form is granted for use with conforming 
HyTime systems and applications as defined in ISO/IEC 10744, provided 
this notice is included in all copies.

The above license is intended to facilitate the use of the formal SGML specifications as a base for developing HyTime applications (particularly when distributed in machine-readable form).

INTRODUCTION TO THE CATALOG

The formal SGML specifications that define the architectural forms appear in the same order as in ISO/IEC 10744. At the right margins of the headings that identify the forms are supplementary comments that identify the clause number and page number of ISO/IEC 10744 where the forms are defined. For example, the line:

Property Name - Clause: 6.7.2 - Page: 36

introduces the "property name" element type form, which is described in clause 6.7.2, which begins on page 36. Consult the standard for the notation and conventions used, which indicate the interrelationships of the forms and their mandatory or non-mandatory status.

An uppercase heading identifies the HyTime module in which the following architectural forms occur. For example, the forms of the measurement module are introduced by the heading:

MEASUREMENT MODULE - Section: 07 - Page: 38

The specifications from Annex A are presented similarly, except that the first-level headings are treated as the equivalent of module names.

CORRECTIONS IN THIS VERSION

Although International Standards are subjected to extensive review and proofreading, early users frequently discover errors. These are reported to the Project Editor for eventual consideration by the responsible standards committee, after which "corrigenda" may be published to correct the errors officially.

Several errors and ambiguities have already been reported; the proposed corrections and clarifications (hereinafter simply "corrections") for some of them are reflected in this document. While it must be stressed that the corrections are not official (and theoretically might never be), they are of such a nature that they are highly likely to be accepted. Corrections affecting only the text of the standard (that is, not the formal SGML specifications included in parts 4 and 5 of this document) are preceded with a currency sign ($).

Corrections added in this version of this Catalog are:

00.1
$In "Measurement module" list item: Change "finite coordinate space" to "scheduling".
06.3.1
$Last paragraph: change "HyTime" to 'the second "HyTime"'.
06.4
$After Note 79 add new para: An element of a type for which the "HyTime" attribute is not defined is a "non-HyTime element:"; it has no HyTime architectural form and therefore cannot affect conformance to the meta-DTD. Both HyTime and non-HyTime elements can occur in its content.
06.4
%resorce: delete from %HyBrid and add to HyDoc inclusions. (Note: inclusion group is now too large for reference concrete syntax, but DTDs can use other means to specify where resources occur.)
06.4.1
HyBrid: delete inclusion group.
06.4.2
nHyTime: change to "sHyTime" ("suppress HyTime element"); only attributes of nested sHyTime elements are processed.
06.4.2
$sHyTime: delete 2nd paragraph and Note 86.
06.5.2
$lexmodel: attribute should be "lexical model element type GIs (lextypgi).
06.5.2.1
$lexmodel: requires support of "lextype" option.
06.5.5.2
dvlist: change "attlist" to "attspecs".
06.6.2
$Second para: change "HyTime NAME nHyTime" to "HyTime architectural form (HyTime)"; move existing last sentence of 2nd para to become last sentence of 1st para; add new last sentence of 2nd para: The value of the "HyTime" attribute indicates whether the entity is to be treated as data or parsed as an SGML document, subdocument, or text entity.
06.6.2
"HyTime" attribute was omitted from formal SGML specification.
06.6.2
$altreps: need not use different data content notations.
06.6.2
insbento: offset changed to "origin 1" like (dimspec).
07.1.1
$Note 142: change "qcnt" to "quantum count".
07.4.1.2
elemref: add "calspec" to reftype group.
08.2.1
locsrc: default value changed to "#CURRENT".
08.3.2.2
nametype: default value changed to "entity".
08.3.2.2
obnames: default value changed to "nobnames".
08.4.1
$Add to 4th para: During concatenation, data content of elements that occur in element content is separated from the data content of siblings by a SPACE character.
08.4.1
catsrce and catres: add additional keywords (catsrcsp and catressp) to indicate when a SPACE character is inserted at each concatenation point.
08.4.2.2
$dataobj: in definition, change "an entity" to "a data entity".
08.4.2.7
$document position: There are two document position properties, for pathloc and treeloc. The marker list contains positive markers only.
08.5.2
notloc: in comment, change "address" to "HyTime address".
09.2.1
linkends: clarifies that one can be omitted, in which case the ilink is the first anchor (for clink compatibility).
09.2.1
ilink: Clarify reftype constraint comment.
09.2.2
clink: Clarify reftype constraint comment.
10.2
fcs: multiple FCS elements of same element type describe different spaces unless they have the same "fcsname" attribute (which requires the "splitfcs" option).
10.3
axisord: omitted axis name means all events occupy full dimension.
10.7
impfcs: type of imposed FCS; change "IDREF" to "NAME".
10.8.1
calspec: respecify content model to remove ambiguity.
A.1.3
arg: balance parentheses.
A.1.3
ATTORCON: balance parentheses.
A.1.3
qpn: balance parentheses.
A.2
HyPD qltnlmgi: "gil" changed to "GIL".
A.2.1.2.2
docpos: clarify as "pathloc document position" and add docpostl: treeloc document position
A.2.1.2.3
KEYWORD: psn=HTsem3; add definition.
A.2.1.2.3
tag: psn=HTsem3.
A.3.1
$HyQ: Add after 4th para: Query args, operands, and other nl nodes are evaluated as they are ordered (left to right), and before the query (or operator or other nl) is evaluated.
A.3.2
$HyQ: Formal definition should be in HyLex (contributions welcomed).
A.3.2
@lc: definition changed to "Value of attribute defined elsewhere"
A.3.2
Delete informal heading "-- HyQ --" and number others A.3.2.1-9.
A.3.2.1
dquery, iquery: allow qdomain without args.
A.3.2.1
qdomain: correct second comment.
A.3.2.1
args: should allow nl as well as nodes.
A.3.2.4
union: clarify description of result nl.
A.3.2.4
inter: clarify description of result nl.
A.3.2.4
diff: eliminate ambiguity between diff and symmetric diff.
A.3.2.6
hylex: balance single quotes.
A.3.2.7
Forall: clarify argument query applies to each nl node in order.
A.3.2.8
Compare: delete comma after "@quantum?".
A.3.2.8
ordered: clarify that overlap refers to position.
A.3.3
HyQ qltnlmgi: "gil" changed to "GIL".
A.5.2.5
Chain: change "feet" to "foot".

ARCHITECTURAL FORMS

USEFUL ELEMENT TYPES, NOTATIONS, AND INSTANCES


HTML markup by Eric Freese - January, 1995
Last update: August 22, 1995